Work status items allow the status of a job (or form) to be recorded. The main usage is in cases where a job needs to be marked as “finished” even though mandatory items on the form have not been completed. For example, an item could not be delivered or a job could not be performed for a particular reason. |
Main |
Main screen for creating/amending a Work status item | ||||||||
*Question | This is the text “label” that is specifying the information that needs to be entered or the question to be answered. Although this is not necessarily a question in all cases, Question is used as the general term to cover the text shown next to an input field. The text should be as short as possible whilst still being self-explanatory. Over-long questions take up a lot of space on PDA screens with their restricted size, so try and make them concise. This text should be an aid to help guide the user through the screen. Any more explanatory text can be made available as “Auditor’s notes” or “Full question text”. | ||||||||
Mandatory |
Tick this box if the question is mandatory and leave it blank if it is optional. This will depend on whether the answer to this question is critical to the data that is being collected, such as signature to confirm customer acceptance. |
||||||||
Default value |
Enter a value that will be inserted without the user doing anything e.g. '0' (zero) for quantity in a supplies list so that only significant entries need to be entered. Sometimes it is appropriate to use values entered by administrators when setting up a job. In this case, use the syntax: $$[unique name used in job definition] |
||||||||
List of complete statuses | A standard list name where the list contains one or more status values which represent a completed job (for example, “Complete, no re-visit required” or “Complete, re-visit required”. | ||||||||
List of incomplete statuses | A standard list name where the list contains one or more status values which represent a incomplete job (for example, “Unable to deliver” or “Unable to gain access”). Selection of any of these values will allow the form to be completed even though other fields remain empty. | ||||||||
Formatting |
Formatting options for a Work status item. | ||||||||
Full screen width? |
This option is usually used in conjunction with multi-line text boxes, giving the user a full-width long text box in which to enter information. This value overrides any formatting set for the section. |
||||||||
Advanced |
Advanced features of a Work status item. | ||||||||
Show as multiple choice |
Tick this box to display statuses as multiple choice rather than a drop-down list. | ||||||||
Auditor's notes |
If you wish to offer the end-user guidance and direction on how to answer a question then use the Auditor’s notes field. This allows you to input any necessary text expanding on the basic question. For the end-user, the auditor’s notes are available via the “right click” option on the device – tap and hold the stylus on the question text. |
||||||||
Don't keep previous result when part of a document lifecycle |
Tick this box if you DO NOT wish data to be collected in this template item to be copied to any jobs created directly from the original form. This is useful for a repeated task (such as booking in/out a rental item or repeated delivery) where the data remains the same but a sign-off is required so this box may be ticked for Date, Surname and Signature. Please note that if a $$transformation$$ option is applied to the newly created job, this setting may be over-ruled. |
||||||||
Full question (for report) |
The question text mentioned above should be framed in such a way as to indicate to the user the information that needs to be input. However, when this information is output on a report via the web site or a PDF additional wording may well be required. Use this field to phrase the original question in a way suitable for the report. |
||||||||
Item flag |
Template item flags are used to apply display classes to $$template item$$ in a consistent and efficient way. They are set up in a system list called Template item flags and might be given names such as Danger so the text appears in red, Disclaimer for smaller text, Long answer to give extra space to the answer. This means that changing the display class can be done in one place rather than on all template items. |
||||||||
*Unique name |
A unique name must exist for everything in a magic5 template. It is so important that magic5 pre-fills the prompt with a non-meaningful name which it will use by default. This does not need to be changed. However, if the data associated with the unique name is to be used elsewhere (for example as part of a calculation, imported or exported, or carried over to a new job), it is helpful to use a meaningful name (such as RefNo, QuantityOrdered, ItemTotal, ContactName, ReasonForReferral) and this meaningful name must be entered before the template is used with real data. If the unique name is changed at a later date, existing data will not be lost but it may no longer be accessible by magic5, in which case it cannot be displayed, used in calculations or exported. It is therefore recommended that this is done only as a last resort and that the original template is duplicated before changes are made - this means that existing data can still be retrieved if necessary. If in any doubt, please contact magic5 support for the best way to deal with this. |
||||||||
|